Determining Service Provider Performance with Ranged Transmissions

ABSTRACT

A network system receives an order request from a requesting device including a list of requested items and a delivery location. The network system may create an order entry by selecting a source location and a provider for the order. The network system sends order information from the order entry to a provider device of the selected provider and a source device corresponding to the source location, where the order information includes an order identifier, a source identifier, and a provider identifier. The provider device broadcasts a beacon including the source identifier and the order identifier. The provider device detects a short range beacon signal from the source device and determines whether the detected source identifier and order identifier match the received source identifier and order identifier from the order information. Responsive to a successful match the provider device verifies its proximity to the source device.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. application Ser. No.16/826,904, filed Mar. 23, 2020, which is a continuation of U.S.application Ser. No. 16/601,514, filed Oct. 14, 2019, now U.S. Pat. No.10,638,297, which is a continuation of U.S. application Ser. No.16/155,124, filed Oct. 9, 2018, now U.S. Pat. No. 10,499,227, which is acontinuation of U.S. application Ser. No. 15/451,221, filed Mar. 6,2017, now U.S. Pat. No. 10,136,288, which claims the benefit of U.S.Provisional Application 62/408,931, filed on Oct. 17, 2016, all of whichare incorporated by reference herein.

BACKGROUND

The described embodiments relate generally to determining serviceprovider or courier behavior, and more particularly to using short-rangetransmissions between wireless devices associated with a courier orservice provider.

Couriers retrieve and deliver items from a source to a destination. Aslarge courier management systems allow a much greater number of ordersand on-demand courier services, often from novice couriers, couriermanagement systems may need to determine and verify when a courier foran order has reached the source of the item to complete pick up of theitem. Couriers at the source point may report the pickup to the couriermanagement system, but this can be unreliable.

SUMMARY

A network system (e.g., a courier or delivery management system)coordinates the delivery of requested items from a source location to adelivery location. A requesting user of the courier management system,such as a customer placing an order for a product or merchandise to bedelivered, may submit an order request by providing input on arequesting device. The requesting user selects one or more items torequest of a plurality of items presented by the courier managementsystem and may optionally input a delivery location. The couriermanagement system is configured to receive order requests from arequesting device. The request includes an identifier associated with anitem provider of the requested item(s), a list of identifiers/tagsassociated with the requested item(s), and/or a delivery location forthe requested items. The courier management system creates an orderentry by selecting a source location that can provide the requesteditems (e.g., based on the identifier associated with the item provider)and selecting a service provider (e.g., a courier, a driver) that canretrieve the requested items from the source location and deliver therequested items to the delivery location. The order entry includesidentifiers (IDs) corresponding to devices, individuals, or entitiesassociated with the selected source location and/or the selectedcourier.

An example of a courier management system is a food delivery system thatcoordinates drivers to deliver food from third party restaurants torequesting users. In this example system, a requesting user, Bob, mightorder a pizza from Joe's Pizza Palace using his smartphone, therequesting device. In this example, the food delivery system wouldtransmit data to a source device associated with and located at Joe'sPizza Palace to notify Joe's Pizza Palace to begin preparing therequested pizza. The food delivery system can select a driver that islocated in the vicinity of Joe's Pizza Palace (e.g., having a currentlocation within a predetermined distance of the location of Joe's PizzaPalace) to pick up the pizza ordered by Bob from Joe's Pizza Palace. Thefood delivery system provides the location of the requesting user to thedriver so that the pizza can be delivered to Bob.

According to some examples, a service provider device (e.g., courierdevice) receives order information from the courier management systemincluding at least a source identifier and an order identifier for theorder. The courier device can enter into a beacon detection mode todetect a short range radio frequency beacon broadcasted by the sourcedevice. The source beacon includes the source identifier of the sourceand the order identifier corresponding to the order entry. Upondetecting the source beacon, the courier device compares the sourceidentifier and/or the order identifier from the detected beacon to thesource identifier and/or order identifier included in the orderinformation received from the courier management system. If the sourceidentifiers and/or the order identifiers match, the courier devicereports to the courier management system that it is in proximity to thesource device.

In some embodiments, the courier device may begin broadcasting its ownbeacon signal including a courier identifier and the order identifier(e.g., in a beacon broadcasting mode). The source device may then detectthe courier beacon and match the courier identifier to a courieridentifier from the order information received from the couriermanagement system. If a match is detected, the source device sends data(e.g., data corresponding to a report) confirming the presence of thecourier device in proximity to the source device to the couriermanagement system. The courier management system may utilize thepresence verification and timing of the received data to improvedestimated completion or delivery times for requesting users, compensatecouriers for waiting times, and/or improve pick up efficiency at sourcelocations by obviating manual confirmation of a pick up by the courier.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an example environment for verifying courier proximity toan order pickup location, according to some embodiments.

FIG. 2 shows example interactions between the courier management system,the source device, and the courier device, according to someembodiments.

FIGS. 3A, 3B, 3C, 3D and 3E are graphical illustrations of the beaconbroadcasting steps performed by a source device and a courier device inorder to verify the proximity of the courier to the source location,according to some embodiments.

DETAILED DESCRIPTION

The figures depict various embodiments for purposes of illustrationonly. One skilled in the art will readily recognize from the followingdiscussion that alternative embodiments of the structures and methodsillustrated herein may be employed without departing from the principlesof the invention described herein.

FIG. 1 shows an example environment for verifying courier proximity toan order pickup location, according to some embodiments. In someembodiments, the environment for verifying courier proximity to an orderpickup location may be implemented in the context of a couriermanagement system 100 which coordinates the delivery of requested itemsbetween users of the courier management system 100, as explained in moredetail below. However, one of skill in the art would be able to applythe proximity verification steps described herein to any system, whichwould benefit from verifying the proximity of two or more mobile devicesto one another. According to this example implementation, there arethree types of users of a courier management system 100: requestingusers, source users, and courier users (e.g., service providers).

Users of the Courier Management System

A requesting user may request items available for ordering from thecourier management system 100 using the requesting device 110. Thecourier management system 100 receives data corresponding to therequested items from the requesting device 110 and generates an orderentry comprising the data (e.g., identifiers) of the requested items.Referring to the example above, requesting user, Bob, may select apepperoni pizza from Joe's Pizza Palace. In this case, the requestingdevice 110 would send data corresponding to the selected pepperoni pizzafrom Joe's Pizza Palace to the courier management system 100. Thecourier management system would then create an order entry representingthe requested pepperoni pizza.

Source users use source devices 120 to receive orders or order entries,and information associated with the order entries (e.g., which items,quantity, special requests, requested time, etc.), from the couriermanagement system 100. Each source device 120 is registered with thecourier management system 100 and each source device 120 is associatedwith a particular source location capable of providing particular itemsthat are available to requesting users. The source data (e.g., sourcedevice and source location, as well as other source related information)can be stored in a database accessible by the courier management system100. After receiving data for an order from the courier managementsystem 100 via the source device 120, a source user may prepare theitems requested in the order at the corresponding source location.

Referring to the previous example, Joe's Pizza Palace has a sourcedevice 120 for an employee (e.g., a source user) to use in order tointeract with the courier management system 100. The source device 120may receive the order for the pepperoni pizza from the couriermanagement system 100 and may then display the order and any additionalinformation associated with the order, such as identifying informationof a courier that will be picking up the order. Employees at Joe's PizzaPalace may then prepare the order based on the displayed information onthe source device.

Courier users can be assigned to pick up and deliver items for ordersfor requesting users and receive information associated with the ordersfrom the courier management system 100 via the courier device 130 (e.g.,such as information indicating the items that must be picked up anddelivered to the requesting user, the locations for pick-up anddelivery, the time to go to the pick-up location, etc.). In someembodiments, couriers may not be strictly couriers and may instead beservice providers who may provide any number of different services(e.g., transport services).

Referring again to the previous example, the courier management system100 may select a courier to deliver the pepperoni pizza from Joe's PizzaPalace to the location of the requesting user. The courier managementsystem 100 may send the location of Joe's Pizza Palace, a list of itemsto be picked up and delivered, and a location of the requesting user thecourier device 130 associated with the user so that the delivery can bemade.

Role of the Courier Management System

The courier management system 100 may coordinate the interaction ofthese three types of users in order to enable items produced by sourceusers at a source location to be delivered to requesting users inanother location by coordinating courier users or service providers. Inan example embodiment in which the courier management system 100 is asystem for arranging the delivery of food orders, the requesting usercan submit a request for a food item from a restaurant in the area, forexample, by generating the request using inputs to select one or moreitems on a dedicated application on a requesting device 110. The couriermanagement system 100, remote from both the restaurant and therequesting user, can create an order (e.g., a record or entrycorresponding to the order) for the food item, store the record in adatabase (e.g., along with data associated with the requested item, therestaurant, the requesting user identifier, etc.), and send orderinformation to a source device 130 located at the restaurant. Thecourier management system 100 can also select, from a pool of serviceproviders, a service provider to provide the delivery service (e.g.,pick up the order and deliver it to the requesting user) and transmitinformation about the order to a courier device 120 of the selectedservice provider or courier. In some examples, each source location isassociated with a source device 130 with which to communicate with thecourier management system 100 over one or more networks. The source userat the restaurant can prepare the food items corresponding to the orderper the received order instructions and wait for the courier to pick upthe food items upon its completion. The courier can confirm pick up ofthe food item and deliver, using navigation instructions, to therequesting device 110 or a delivery location specified by the requestinguser to deliver the food item.

In addition to communicating with source users, courier users, andrequesting users to arrange for the delivery of items from the sourcelocations to the requesting users, according to some examples, thecourier management system 100 coordinates the use of short range radiotransmissions between the devices to verify the proximity, location,and/or movement of a courier device 130 (e.g., relative to a sourcedevice) and determine additional data, which may be used to improveestimated times of arrival, provide incentives for couriers, and/orimprove courier adherence to instructions provided by the couriermanagement system 100.

Requesting Device

The requesting device 110 provides an interface, via a clientapplication for example, for an end user to request items made availableby the courier management system 100 via an order request module 112.The requesting device 110 may be any suitable computing device that candisplay items available for request and a graphical user interface (GUI)for the end user to select those items (e.g., via an input mechanism,such as a touch sensitive display). The client application can receivedata from the courier management system 100 about the various sourcesand/or items that a requesting user can order (e.g., based on a time,the delivery location or current location of the requesting user, and/orthe source locations), and the request module 112 can generate andpresent (for example, in conjunction with a user interface module, notillustrated in FIG. 1 for purposes of simplicity) a user interface thatincludes a set of selectable features or graphic images representingsources (e.g., restaurants, stores, etc.) and/or a set of selectablefeatures representing items that a requesting user can order. Forexample, the GUI may display icons representing a variety of foodestablishments and, upon receiving a user selection of one of the icons,the GUI may display various food items available at the selectedestablishment.

The request module 112 determines, via an input detected or receivedfrom the requesting user, data indicating one or more requested itemsand sends a set of identifiers of the requested items (and/or anidentifier of the source that provides the requested items) to thecourier management system 100 over one or more networks 140 as a requestto the courier management system 100. The location of the requestingdevice 110 may be sent as part of the request to the courier managementsystem 100 and may also be used as a delivery location for the order.Additionally or alternatively, the requesting user may also provide adelivery address.

Functions of the Courier Management System

The courier management system 100 receives requests for items from arequesting device 110 and coordinates preparation of the order by asource location, as well as pickup and delivery of the contents of theorder by a courier operating the courier device 130. In one example, thecourier management system 100 includes an order creation module 105, acourier selection module 106, and a courier order verification module104. In addition, the courier management system 100 has one or more datastores, such as an order data store 102, a source location data store108, and a courier data store 109, for example. The courier managementsystem 100 may arrange courier services for many different types oforders depending on its configuration. Referring back to the pizzaexample, the source would be a restaurant and the order would specifythe particular pizza from the menu of the restaurant which a courierwould then retrieve and deliver. Another example is the delivery ofitems such as store-bought products by a user, or items that are to bedelivered from one location to another, such as packages, courtdocuments, etc. The courier management system 100 thus may include manyadditional components, which for purposes of simplicity are notillustrated in FIG. 1, that assist in the order process. For example,the courier management system 100 may also perform a selection of aspecific courier for delivery of a particular order (e.g., based on thestatus of the courier and/or the location of the courier, the locationof the restaurant or store, the location of the destination, etc.), andmay provide payment, order selection, and other services for the usersassociated with the requesting device 110, the source device 120, and/orthe courier device 130.

Upon receiving a request for one or more items from requesting device110, the courier management system 100 creates an order entrycorresponding the requested items using the order creation module 105.For example, the order creation module 105 can create and store an entryin the order data table or store 102. The order creation module 105generates a unique order identifier for the new order (e.g., randomstring for the identifier) and lists the items (e.g., as identifiers ortext) corresponding to the order along with a delivery location, whichmay be an address or GPS location provided in the request.

In one example, the order creation module 105 then selects a sourceand/or source location for the order. For systems where the sourcelocation for the requested items is included in the request, the ordercreation module 105 looks up the corresponding source identifier fromthe source location data store 108 and adds the source identifier to theorder entry. As an addition or an alternative, in some examples, therequest can include the source identifier along with the identifiers ornames of the items. In such an example, the order creation module 105can identify the source and the source location using the sourceidentifier. In systems where the source location or source identifier isnot included in the request, the order creation module 105 uses thesource location data 108 to determine which source locations can providethe requested items.

After determining the source identifier for the order entry, the ordercreation module 105 provides request data including the source locationand delivery location to the courier selection module 106 to cause thecourier selection module 106 to select a courier associated with acourier device 130 to deliver the requested items from the sourcelocation to the delivery location. Depending on the embodiment, thecourier selection module 106 may select a courier based on a number offactors, including the address or GPS location of the source location(e.g., the GPS location), the GPS location of requesting device or thespecified delivery location, and the location of the courier device; thecurrent location or route of the courier; the distance of the courier tothe source location; and/or the estimated travel time from the locationof the courier device to the source location and then to the location ofthe requesting device. The courier management system 100 monitors theabove listed factors by periodically communicating with and/or receivingupdates of the courier data to reflect changes in courier positions,routes, states, etc. In some embodiments, the courier selection module106 may select a courier for the order entry and then send datacorresponding to an invitation to provide the delivery service to thecourier device 130. The courier may then choose to confirm or deny theinvitation, e.g., by providing user input. If the invitation is denied,the courier selection module 106 selects a different courier to completethe order. If the invitation is accepted, the courier selection module106 updates the order entry with the selected courier identifier and/orstores other information or associates the order entry with otherinformation, such as the location of the courier when accepted, theroute the courier is taking, etc. In addition, once the courierselection module 106 has successfully arranged a delivery for the order,information about the selected courier is provided to the requestingdevice 110 and/or the source device 120.

Accordingly, in some examples, the completed order entry includes aunique order identifier, a source identifier, a courier identifier, arequesting user identifier, a set of data corresponding to the requesteditem(s), and/or a delivery location. The order entry can also include orbe associated with other information, such as time of request, time oforder preparation completion, time of pick up, estimated time of arrivalto delivery, route driven or taken by the courier, duration of time frompick up to delivery, etc. An order entry may also include an indicationof the status of the order (e.g., whether the order is “beingprocessed,” “being prepared,” “being picked-up,” “en route,”“delivered,” etc.).

After the order creation module 105 creates the order entry for therequested items, the courier order verification module 104 sends datacorresponding to the order entry (e.g., information or identifiers ofthe items requested by the user of the requesting device 110) to thesource device 120 and/or the courier device 130, where it is stored inorder data 122 and/or order data 136 respectively. Order data 122 and/ororder data 136 may be synchronized (e.g., periodically and/or responsiveto any changes to the order entries in the order data store 102) withthe order entry stored at the order data store 102. The source devices120 and courier devices 130 may maintain order entry data for “activeorders.” An active order may be any order that has been requested on thecourier management system 100 that has not yet been delivered to thedelivery location. In some embodiments, an order entry may remain storedin the order data store 102 after it has been delivered (e.g. to recordfeedback on the order in association with the order entry). In someembodiments, data associated with inactive orders are cleared from orderdata 122 and order data 136 on source devices 120 and/or courier devices130. Each source device 120 and each courier device 130 may manage morethan one active order at a particular time. When the status of an orderchanges the source devices 120 and courier devices 130 may be updatedwith the new status of the order. Additionally, the status of the ordermay cause changes in behavior of the source devices 120 and courierdevices 130.

The source device 120 provides an interface (e.g., via a clientapplication or web page on a browser) to an operator at the sourcelocation to interact with the courier management system 100, andbroadcasts a beacon for the courier device 130. The source device 120may be any suitable computing device, such as a desktop or laptopcomputer, a point-of-sale terminal with suitable features, a mobiledevice, a smartphone, a tablet computer, and so forth. In one example,the source device 120 can be a tablet device that is coupled to orcommunicates with the merchant's point-of-sale terminal, while inanother example, the source device 120 can correspond to thepoint-of-sale terminal. The source device 120 includes order data 122,as well as an order pickup module 124. The order data 122 includes orderentries for orders that can be provided at the source locationcorresponding to the source device. The source device 120 also includesa short range transceiver 126 for broadcasting and receiving beacons.The short range transceiver 126 transmits a source beacon 150 accordingto instructions from the order pickup module 124 and may receive ordetect a courier beacon 152 from the courier device 130.

The short range transceiver 126 may take various forms according todifferent embodiments. In general, the short range transceiver 126 emitsa low-power, low-range signal that may be detected by other nearbydevices, such as, for example, the courier device 130. In oneembodiment, the short range transceiver is a radio transceiver, and thesource beacon 150 is transmitted via a Bluetooth broadcast or BluetoothLow Energy (BLE) broadcast. In a particular embodiment, the beacon maybe transmitted using Bluetooth technologies and/or protocols thatprovide received signal strength ranging and/or identificationinformation, which identifies the broadcasting device, may be used. Inan embodiment, the beacon broadcast includes a unique identifierassociated with the broadcaster, and may specify a major and a minorvalue. The unique identifier (e.g., a UUID) can be associated with thecourier management system 100 and may be common among all source andcourier devices interacting with the courier management system 100. Inthis example, the major value represents the individual broadcastingdevice, such as the source device identifier or the courier deviceidentifier, while the minor value is an identifier of the order. Thecourier order verification system 100 may provide these identifiers foran order to the source device 120 and the courier device 130. The minorvalue for broadcasting of the order may represent a hash value or othermeans of converting an order to a range of possible values for thebroadcast. For example, the major and minor values each have a rangebetween 0 and 65535, and the courier management system 100 determinesnear-unique values for an expected interaction between courier device130 and source device 120. For example, the major value may be adjustedsuch that each source and courier device in a nearby location has adistinct major value.

A similar transceiver is also provided on the courier device 130 as ashort range transceiver 132. The transceiver may also use differentamounts of power when broadcasting compared to when transmitting. Asdiscussed below, in one example, the transceiver on the courier device130 may maintain operation as a receiver only (to detect a source beacon150). Additionally, the courier device 130 may broadcast a courierbeacon 152 to the source device 120 upon receiving a source beacon 150from the source device 120.

When receiving or detecting a beacon, both the source device 120 and thecourier device 130 may parse the broadcast beacon to identify the orderidentifier or the source or courier identifier (e.g., the major valueand minor value). In addition, the transceiver of either the courierdevice 130 or the source device 120 (or in conjunction with other deviceresources of the courier device 130 or the source device 120) maydetermine the signal strength of the beacon, and use the received signalstrength to an estimated proximity or distance of the sending device(e.g., converting the received signal strength). In someimplementations, the estimated proximity is reported directly as adistance measurement. In other embodiments, the estimated proximity maybe reported qualitatively as a proximity classification, for example, as“far,” “near,” or “immediate” to the receiving device. Additionally,proximity classification may correspond to a range of estimateddistances depending on the implementation of the short range transceiver126. For example, a proximity of 10 meters or more may be reported as“far”, between 1 and 10 meters as “near”, and within 1 meter as“immediate”. Therefore, the received signal strength of the broadcastsignal may be converted to an estimated distance before being assigned aproximity classification as a proximity estimate and reported to thecourier management system.

The short range transceiver 126 may also be capable of transmitting asingle beacon at any given time. The order pickup module 124 receivesorders from the courier management system 100 and instructs the shortrange transceiver 126 in the broadcast and detection of beacons. Whenthe order pickup module 124 receives an order from the couriermanagement system 100, the order pickup module 124 may provide the neworder on a user interface for display, for example, for an operator atthe source to begin preparing the items in the order for pickup. Theorder pickup module 124 may also add the order to a data store of orderdata 122. In one example, the order data 122 maintains a list ofcurrently active orders. As referred to herein, the active orders arethe orders which have not been picked up by a courier, and which thesource device 120 will broadcast for a courier device 130 to identify.

To identify the source device 120, the order pickup module 124 controlsthe short range transceiver 126 to broadcast active orders with a sourcebeacon 150. In one example, the source beacon includes a sourceidentifier and an order identifier. In such an implementation, these maycorrespond to the major and minor values of the beacon, respectively.The order pickup module 124 identifies the active orders in the orderdata 122 and broadcasts the active orders via the short rangetransceiver 126 to provide the source beacon 150 to devices that arenear to the source device 120. When a device is near to the sourcedevice, such as the courier device 130 assigned to one of the activeorders, the device may receive and detect the broadcast source beacon150 and identify the values within the source beacon 150.

In addition, the transmission of a beacon may be limited to broadcastinga single message or identifier on the channel at once. In embodimentswhere the short range transceiver is limited to transmitting a singlesource beacon 150, the order pickup module 124 may modify the defaultbehavior of the short range transceiver 126 to cycle the broadcast ofactive orders. That is, among the set of active orders, each activeorder may be broadcast for a limited amount of time and then anotherorder from the set of active orders is selected for broadcast, untileach of the active orders has been broadcast, and then the first ordermay be broadcast again. As active orders are added or removed to thelist of active orders, the orders cycled by the order pickup module 124for broadcast (and the associated beacons) may also change. In this way,a given source device 120 may broadcast a consistent source identifier(e.g., as a major value) and may modify the broadcast order identifieras the active orders are cycled. Each active order may be broadcast fora specified amount of time, such as one tenth of a second (or a completesecond, or other specified time), or the amount of time for cycling theorders may vary, such as according to the number of active orders. Forexample, the entire set of active orders may be set to cycle within aspecified amount of cycle time, such as thirty or sixty seconds. Eachorder may receive a proportional amount of that cycle time, for examplewhen there are six active orders, each may be broadcast for ten secondsof a sixty-second cycle time. In this way, according to an example, thecourier device 130 that receives any broadcast having an expected sourceidentifier may wait for the predetermined full cycle time to verifywhether the source device 120 is transmitting an active order desired bythe courier device 130.

The order pickup module 124 may also monitor received courier beacons152 from the short-range transceiver 126. When a courier beacon 152 isreceived, the order pickup module 124 identifies whether the receivedcourier beacon 152 matches an active order of the source device 120 andidentifies a match in the order data 122. When there is a match, theorder pickup module 124 may send a notification to the couriermanagement system 100 to indicate the receipt of a courier beacon 152and verify the courier is nearby. In some embodiments, the order pickupmodule 124 sends updates to the courier management system 100 as theestimated proximity of the courier device changes. For example, when theproximity of a device matching an order changes to “near” from “far” orfrom “near” to “immediate.” In some examples, the source device 120 doesnot send the event until the received courier beacon 152 that matches anactive order is closer to the source device 120 than a threshold, forexample by not notifying the courier management system 100 until thecourier beacon is an estimated “near” proximity. After receiving thecourier beacon 152 (or receiving it at a given estimated proximity), thesource device 120 may remove the related order from the list of activeorders. Alternatively, the source device 120 may report the receivedcourier beacon 152 but maintain the order in its list of broadcastactive orders until receiving a message from the courier managementsystem 100 to stop broadcasting.

The courier device 130 also receives order data from the couriermanagement system 100 and receives and/or broadcasts beacons to verifyproximity of the source device 120 with the courier device 130. Like thesource device 120, the courier device 130 can be any suitable computingsystem, such as a mobile device or smartphone. As with the source device120, the courier device 130 receives and stores order data 136, and acourier order module 134 may receive and coordinate orders from thecourier management system 100. The short range transceiver 132 is alsocapable of receiving the source beacon 150 and may also be used tobroadcast a courier beacon 152.

When the courier device 130 has one or more active orders, the courierorder module 134 instructs the short range transceiver 132 to listen forany source beacons 150 having a source identifier and order identifierassociated with any active orders. In this example, the courier ordermodule 134 may instruct the short range transceiver 132 to operate in abeacon detection mode to detect beacons, and does not broadcast acourier beacon 152 until an appropriate source beacon 150 for an activeorder is received. In this example, the courier order module 134 mayreduce the power consumption of the short range transceiver by avoidingbroadcast until the courier device 130 detects the relevant sourcedevice 120. As an addition or an alternative, in some embodiments, thecourier order module 134 does not detect beacons using the short rangetransceiver 132 until other data (e.g., GPS data) indicates that thecourier device 130 is close to the source device 120. For example, thelocation of the courier device 130 may be otherwise monitored, and thecourier order module 134 may not activate the short range transceiver132 to detect source beacons until the location of the courier device iswithin a threshold distance from the source location, or a geofence orother location area of the expected location of the source device 120.The location area and determination thereof may be performed by thecourier management system 100 or may be performed by the courier device130. In a particular embodiment, the courier device 130 is equipped witha GPS receiver and reports its GPS location to the courier managementsystem 100. The courier management system 100 may then notify thecourier device 130 that it is currently located within a geofenceassociated with a source corresponding to one of the active orders inthe order date 136 of the courier device 130.

When the courier order module 134 receives a source beacon 150 matchingorder data 136, the courier order module 134 determines the receivedsignal strength of the received source beacon and calculates a proximityestimate based on the received signal strength. The courier order module134 reports the match to the courier management system 100 andoptionally includes the calculated proximity estimate. As with thesource device 120, the courier order module 134 may continuously detect(e.g., periodically sample at a predetermined rate) the source beacon150 and recalculate the proximity estimate based on changes in thereceived signal strength of the beacon. If the proximity estimatechanges between samples, the courier order module 134 may send an updateof the estimated proximity of the source device 120 to the couriermanagement system 100 as a beacon detection event. In some embodiments,a change in the proximity estimate is reported to the courier managementsystem only when the proximity estimate changes from one proximityclassification to another.

In addition, in one example, when the courier device 130 receives abeacon having a source identifier and/or an order identifier matchingthe order data 136, the courier device 130 may begin to broadcast acourier beacon 152 for the courier (e.g., as a confirmation of detectingthe source beacon 150). The courier beacon 152 may include the courieridentifier as well as the order identifier for receipt by the sourcedevice 120. The courier beacon 152 may be broadcasted when the sourcedevice 120 is identified, or may be broadcast when the estimatedproximity of the source beacon is relatively closer to the courierdevice 130 (e.g., “near” or “immediate”). In this way, broadcast of thecourier beacon 152 may be limited to circumstances when the sourcedevice 120 is expected to receive it and reduce the comparatively energyexpensive broadcasting of the courier beacon 152. In one example, thesource device 120 reports receipt of the courier beacon 152 to thecourier management system 100.

In an alternative embodiment, the courier device 130 may broadcast thecourier beacon 152 before detecting a source beacon 150 and the sourcedevice 120 can detect or receive the courier beacon 152. For example,the courier device 130 can be triggered to broadcast the courier beacon152 in response to the courier device 130 and/or the courier managementsystem 100 determining that the courier device 130 is within apredetermined distance of the location of the source device 120 or thesource location. The courier device 130 and/or the courier managementsystem 100 can periodically determine the current location of thecourier device 130 using the location-based resource(s) of the courierdevice (e.g., a global positioning system (GPS) receiver, Wi-Fitransceiver, etc.) and compare it with the location of the source device120 (or the address of the store, restaurant, venue, etc. where thesource device 120 is located).

The various devices may also communicate with one another using anetwork 140, which may represent the public Internet, or another type ofcommunication channel. In general, each device may connect to thenetwork using various means, such as a wired or wireless connection(cellular, LAN, WAN, etc.). Though the source device 120 and courierdevice 130 may communicate via the network 140 to the courier managementsystem 100, and potentially with each other, via the network 140, thesesystems typically are not configured to permit estimated proximityinformation as may be provided by the beacons as described herein.

As described above, the source device 120 may broadcast (e.g., based onthe status of the order etc.) a beacon 150 including an identifier forthe order and/or an identifier of the source device 120. By broadcastinga source beacon 150, the source device 120 enables courier devices 130to determine their relative location to the source device 120. In someembodiments, the device that detects a beacon may report its proximityto the device broadcasting the beacon in discrete intervals. Forexample, a device may report that it is within 15 meters, 10 meters, and5 meters. This may aid in the pickup and delivery process of satisfyingan order from a requesting user and may provide, through an eventreporting processes described below, useful positioning and performancedata to the courier management system 100.

The source device 120 may broadcast a source beacon 150 for a particularorder when the status of that order indicates that the requested itemshave not yet been obtained, by the courier, from the source location.For example, the source device 120 may be instructed to broadcast asource beacon 150 for a particular order when the status of that orderindicates that the requested items of the order are “ready for pickup.”In this manner, the source device 120 can be instructed to broadcast asource beacon 150 during any identified stage in the order deliveryprocess. By selectively broadcasting the source beacon 150, the sourcedevice 120 may reduce the number of beacons being broadcasted at a giventime while still providing location information to nearby courierdevices 130 that have been designated to obtain requested items from thesource location.

When a courier device 130 comes within range of the source device 120,the courier device 130 can detect the source beacon 150 and theidentifier(s) included in the source beacon 150. The courier device 130may then determine whether the order identifier included in the sourcebeacon 150 matches an order identifier associated with any active ordersof the courier (e.g., associated with the courier's account or thecourier device 130). If the order identifier included in the sourcebeacon matches any order identifiers associated with the courierdevice's active orders, the courier device 130 reports the event ofdetecting the source beacon 150 (e.g., transmits data about the event asa “beacon detection event”) to the courier management system 100. Insome embodiments, upon receiving the reported event, the couriermanagement system 100 may change the status of the order or may recordthe timing of the event for later processing.

According to some examples, by having each device report receipt ofspecific beacons, the courier management system 100 can verify that thecourier device 130 was actually in range of the source device 120 orvice versa (e.g., to prevent fraud or spoofing of the respectivebeacons). As an additional benefit, the courier device 130 may saveenergy by waiting to broadcast its courier beacon until after receivingor detecting the source beacon 150, as the energy cost of detectingbeacons may be much lower than the cost of broadcasting a beacon. As thecourier device 130 may typically be moving and less reliably connectedto a power source, this conserves power on the courier device 130 untilthe broadcast is expected to be received by the appropriate sourcedevice 120 (e.g., until after the courier device 130 receives thedesired source beacon 150 and is therefore in range of the source device120).

The courier order verification module 104 receives data about beacondetection events (e.g., including time information and/or locations ofthe devices when the beacon detection event occurred) from the sourcedevice 120 and/or the courier device 130 and determines whether thecourier device 130 and the source device 120 were proximate to oneanother. This data may be used, for example, to verify that the orderwas picked up by the correct courier, or that the courier picked theitem up in a way that brought the two devices in near proximity to oneanother. As a further example, couriers may be required by a policy ofthe courier management system 100 to enter the premises of a building atthe source location to retrieve the order. If the order is picked up(e.g., the respective user of the source device 120 and/or the courierdevice 130 provides input indicating pick up was completed), but thecourier did not enter the source location (e.g., did not enter thebuilding), the courier order verification module 104 may be able todetermine that the courier did not follow the policy because no eventwas received indicating the devices were in proximity to one another. Insome embodiments, the dimensions of the building at the source locationas well as the location of the source device 120 within the building maybe used along with the detection event to determine whether a courierentered a building. In another example, the beacon detection events canbe used to determine how long the courier had to wait at the sourcelocation once he/she entered in order to receive the physical order fromthe source location and/or determine the delay by the source inpreparing the order for pick up (e.g., based on an estimated time ofpreparation).

In some examples, the courier order verification module 104 provides theorder information to each of the courier device 130 and source device120. As discussed below, in some examples, the source device 120 maybroadcast a source beacon 150 that is received by the courier device130. The courier device 130 reports the receipt of the source beacon 150via a beacon detection event. The courier device 130 may also broadcasta courier beacon 152, which when received by the source device 120, isreported in another beacon detection event. When the courier orderverification module 104 receives data about the detection events, whichmay include an estimated distance between the courier device 130 and thesource device 120, the courier order verification module 104 candetermine that the two devices were actually proximate to one anotherand verify that the order was picked up. This may also permit thecourier order verification module 104 to limit interactions on thesource device 120 or on the courier device 130, for example, byobviating manual confirmation that an order was picked up by either thesource user or the courier using the source device 120 or the courierdevice 130, respectively.

According to an example, the courier order verification module 104 sendsthe source identifier and/or courier identifier to the source device 120and the courier device 130 for broadcasting the source beacon 150 andcourier beacon 152, respectively. In some embodiments, the courier orderverification module 104 may also instruct the source device 120 and thecourier device 130 to start and/or stop broadcasting a beacon for theorder. For example, when the courier device 130 broadcasts a courierbeacon 152 in response to detecting the source beacon 150, the courierorder verification module 104 may instruct the courier device 130 tostop broadcasting the courier beacon 152 when the courier managementsystem 100 receives the associated beacon verification event from thesource device 120. This can result in power savings on one or bothdevices.

In one variation, the courier order verification module 104 may also usedata about detection events to determine how long a courier waits at thesource location, and thus may be used to determine wait times of thecourier, for example, to provide compensation to the courier for thedelay, or to better estimate the delay of a pick up at the sourcelocation (e.g., based on an average of a plurality of wait times by aplurality of couriers at the source location). Additionally, theexpected wait time at the source location may be used to automaticallydetermine how long a courier is expected to wait and better predictand/or schedule the time of selecting a courier and/or the arrival of acourier at the destination of the order. The courier management system100 may also provide mapping and navigation services, in which case theamount of time that a courier 130 is delayed at the order pickuplocation may be used to better predict courier routing, provide anestimated delay, and further improve courier routing, travelcoordination, and other features provided by the courier managementsystem 100. In this example, the length of time that couriers are at thesource location may be determined by receiving events when the nearbybeacons detected by the courier device 130 change, such that the courierdevice 130 reports when it exits the range of the source device 120. Thewait time for one order may be stored with the wait times of otherorders to determine the average wait, a distribution of wait times,and/or other characteristics of the wait times for a particular sourcefor use in determining routing, travel estimates, and/or delivery timesto the arrival as noted above.

Updates for the order may also be provided to the order request module112 of the requesting device 110 associated with the order. For example,when an order is verified as picked up by the courier order verificationmodule 104, the courier verification module 104 may provide anotification to the order request module 112 to update the userinterface, e.g., via the client application, and indicate that the orderhas been picked up by the selected courier, and may update estimatedtravel and delivery times based on the average wait time of a courier atthe source location, or may update the delivery time when the courierdevice 130 no longer receives (or receives at a lower strength) beaconsbroadcast by the source device 120.

FIG. 2 shows example interactions between the requesting device 110, thecourier management system 100, the source device 120, and the courierdevice 130, according to some embodiments. The requesting device 110 mayreceive 200 input from the requesting user regarding requested itemsand, optionally, an input indicating a desired delivery location. Therequesting device then sends 201 an order request including a list ofrequested items (e.g., a set of item identifiers) and a deliverylocation (e.g., a GPS location or address) to the courier managementsystem 110. In some examples, the delivery location is reportedautomatically as the GPS location of the requesting device 110. Thecourier management system 100 generates 203 a new order entry inresponse to receiving the order request. To generate 203 the orderentry, the courier management system 100 may satisfy the received orderrequest by selecting a particular source location that can provide therequested item. In another example, the source location may be specifiedin by the order request. Upon selecting the source location anddetermining the corresponding source device 120 the courier managementsystem 100 may select a courier with courier device 130 that isavailable to pick up the requested item. Upon selection of a sourcelocation and courier a new order is generated 203 at the couriermanagement system 100, and the courier management system 100 sends 205the new order information to the courier device 130 and the sourcedevice 120. The order information includes the identifiers associatedwith the order including the order identifier, the courier identifier,and/or the source identifier. Order information may be sent to thecourier device 130 and the source device 120 over network 140. Inembodiments where the courier immediately delivers the retrieved item toa requesting user, the order information may also include identifyinginformation for the requesting user. The order information may alsoinclude additional details associated with the order such as the orderinstructions (e.g. order description, order instructions, a pick-up timefor the order, etc.), courier descriptive information (e.g. a pictureidentifying the courier, the courier's name, courier vehicle, etc.), andpickup instructions for the courier (e.g. steps for picking up the orderat the source location, parking regulations outside of the sourcelocation, etc.). Alternatively, these details may be retrieved from thecourier management system 100 by either source device 120 and/or courierdevice 130 as needed using the order identifier, source identifier, orthe courier identifier.

After receiving the order information including the order identifier andsource identifier, courier device 130 may initiate a beacon detectionmode 210 to listen for a source beacon 150 that includes an orderidentifier and a source identifier that matches the received orderinformation stored in order data 136. Additionally, the source device120 adds 215 the received order to the broadcast of the source device120. The source device 120 broadcasts 218 source beacons 150 includingthe source identifier and the order identifiers corresponding to theactive orders in order data 122. The broadcast source beacons thus mayinclude the newly-received order, and may include broadcastingadditional active orders and including the new order as one of theorders in a broadcast cycle of orders.

Initially, the courier device 130 is typically not within range of thesource device 120 to receive a beacon (e.g., the courier operating thecourier device 130 may be in a different geographic region and travelingto the merchant or location of the source device 120). As the courierapproaches the source or merchant, the courier device 130 may detect orreceive source beacons 150 that are broadcasted from the source device120. The courier device 130 may then check the orders against activeorders at the courier device 130 to determine whether there is a match.If the source identifier and the order identifier of a received beaconmatches 220 an active order, the courier device 130 may send 225 acourier verification to the courier management system 100 to verify thatthe courier device 130 has come within range or has entered the vicinity(e.g., has come within a predetermined distance) of the source device130. This verification may be sent as a beacon detection event by thecourier device 130. In some embodiments, the process may end after thisstep, such that the courier verified its proximity to the source to thecourier management system 100. In alternative examples, the courierdevice 130 may continue to monitor its proximity to the source devicevia the broadcast beacons from the source device, and report changes tothe courier management system 100 as additional beacon detection events.By continuing to report the proximity of the courier device 130 to thesource device, the courier management system 100 may update theestimated time of delivery for the order based on the amount of timespent waiting for pickup of the order or the time at which the courierdevice 130 reported leaving the proximity of the source device 120. Ifthe courier device 130 continues to report its proximity until it leavesthe range of the beacon, the proximity information may be used todetermine how long the courier device 130 was near the source to pick upthe order. This may reflect delays or other problems with the pickup orpreparation by the source of the order, or to notify the couriermanagement system 100 when the courier device 130 leaves the range orvicinity of the source device 130. In some embodiments, detecting a pickup delay based on the beacon detection events may cause the couriermanagement system to notify the requesting user of a delay in thedelivery of the requested items.

As an addition or an alternative, in some embodiments, the courierdevice 130 can also broadcast 230 its courier beacon 152 in response tosending 225 the courier verification. In this alternative embodiment,the courier device 130 may begin broadcasting 230 a courier beacon withthe order identifier and the courier identifier corresponding to theorder. Upon receiving the courier broadcast 152, the source device 120identifies 235 a match between the courier and an active order, andsends a source verification 240 to the courier management system 100.The source verification may be a beacon detection event sent from thesource device 120. When the courier management system 100 receives thecourier verification, and optionally when it also receives the sourceverification, the courier management system 100 may automatically verify245 that the order was picked up by the courier, as the devices reportedproximity to one another for specifically designated broadcastparameters by the other device. In some embodiments, when the order isverified 245 as picked up, the courier management system 100 mayindicate to the courier device 130 and source device 120 to stopbroadcasting 250, 255. In some embodiments, the courier managementsystem 100 instructs the courier device to stop broadcasting 250 priorto instructing the source device 120 to stop broadcasting 255. Forexample, though the proximity of the devices has been verified, theorder may not in fact be ready to pick up, or there may be otherproblems with the courier device 130 leaving the source location. Inthis case, by allowing the source device 120 to continue to include theorder in its broadcast, the courier device may continue to report theestimated proximity of the source device 120 to the courier managementsystem 100. Thus, the courier management system 100 may delay a commandto stop the broadcast of the source device 120 until after the courierdevice 130 reports a change in proximity of the courier device 130 fromthe source device 120 (e.g., from near to far). In other examples, thecourier device 130 continues to report any change in proximity to thesource device 120 by monitoring the “source identifier” of broadcastbeacons, rather than the specific order. In that case, theactively-broadcasted orders on the source device may remove the verified245 order, but events may still be received and provided by the courierdevice 130 representing the proximity of the courier device 130 to thesource device 120.

By providing the receipt of a source beacon and matching source andorder identifiers, the courier management system 100 can moreeffectively determine whether couriers are properly approaching thelocation of the source device to complete an order pick up. In addition,in embodiments where the courier device 130 broadcasts a courier beacon152, because the courier device 130 and the source device 120 areproviding dual confirmation of each other's proximity, the location of abeacon cannot be easily spoofed.

According to some examples, an entity that provides a platform forenabling delivery services and/or arranges courier services via thecourier management system 100 can use the verification data to determinehow long individual couriers are at an order provider's locale or venue(e.g., within a restaurant or a store, or a delivery location, etc.)generally or for each particular order. The entity can offer financialincentives, for example, to reduce dissatisfaction for couriers havingto wait an extended amount of time for orders to be ready by the orderprovider or merchant. For example, a courier may be instructed to arriveat a restaurant to pick up a food order at noon. If the courier hasarrived at 11:58 am and had to wait until 12:25 pm for the food order tobe ready for delivery, the courier management system 100 can determine afinancial incentive amount based on an extra duration of time that thecourier had to wait (e.g., excluding a five-minute buffer from noon to12:05 pm, the financial incentive amount can be based on the courierhaving to have waited for an extra twenty minutes).

Still further, in some examples, based on the data collected forindividual order providers (e.g., from historically obtainedverification data for orders in general and/or for specific items oforders), the courier management system 100 can predict when a receivedorder for a particular order provider will be ready for pick up. Byusing the predicted estimated time of order completion, the couriermanagement system 100 can time when a courier needs to be selected froma pool of available couriers and drivers to head to that order provider.As an additional example, the courier management system 100 can also usedetermined information about actual wait times or order completion timefor an order provider to provide more accurate estimated time of arrival(ETA) information to requesters/consumers of the order.

The verification data can also be used to inform the entity whether acourier has followed particular instructions for picking up an order. Asan example, for a particular restaurant, any food order pickups mayrequire a courier using the platform to go inside the restaurant to pickup the food order (e.g., as opposed to asking someone at the restaurantto come to the courier's vehicle to hand off the food order). Thecourier can be instructed, via a client application running on thecourier device 130, to go into the restaurant. The courier managementsystem 100 can use proximity information determined from the beacons todetermine whether a courier has complied with the instructions andprovide feedback to the courier, e.g., via the client application, tomodify or improve behavior (or provide positive feedback for followingthe instructions).

According to another example, by using beacons, the source device 120can automatically detect whether a courier was present to pick up anorder. An operator at the source and/or the courier may not have topress a button or a soft feature on a respective device to confirm thatan order was picked up, thereby minimizing manual hand off andconfirmation between the parties. In additional configurations, thereceived beacons may also be used to modify the interaction and displayby each device. As one example, when a courier beacon is received by thesource device 120, the source device 120 may retrieve a picture of thecourier associated with the device to display the picture and order fordelivery to the operator of the source device 120, permitting easyidentification and hand-off to the courier and reducing the risk ofimproperly giving an order to an unauthorized user. This may also enablean operator at the source to make it easier to find the correct courier(if there are multiple couriers or a crowd of people at the venue).Alternatively, or additionally, upon detecting a source beacon 150 thecourier device 130 may retrieve the contents of the order for pickup andinstructions for picking up the order. This process allows the courierto verify whether they have received to correct order for pickup andwhether they are satisfying the requirements of the venue operating thesource device.

In another example, a similar beacon process may be performed during thedelivery process, such that the courier may use beacons to identifyproximity to the desired delivery location of the requesting device 110.

FIG. 3A illustrates a courier with a courier device approaching a sourcelocation in accordance with some embodiments. FIG. 3A illustrates abird's eye view of a building of the source location 300 and thesurrounding streets. Within the source location 300, the source device302 is located on a counter top. As previously described, the sourcedevice 302 is broadcasting a source beacon 150. FIG. 3A illustrates thebeacon signal as having a source beacon detection range 304 and a beaconpickup proximity 306. In this example illustration, the source beacondetection range 304 is the range at which a courier device 308 is ableto detect the source beacon 150 and the beacon pickup proximity 306indicates the proximity to which the courier device 308 must be in orderto be confirmed as having picked-up the requested items of an order. InFIG. 3A, the courier device 308 is located outside of the source beacondetection range 304 and is travelling in a courier vehicle 310, whichmay be any kind of vehicle.

Because the courier device 308 is located outside of the source beacondetection range 304, the courier device 308 cannot detect the sourcebeacon and so does not transmit a beacon detection event to the couriermanagement system 100.

FIG. 3B illustrates a situation where the courier device 308 has movedinside the source beacon detection range 304 in accordance with oneembodiment. In this case, the courier has parked the courier vehicle 310outside the source location 300 and has moved inside the source location300 with the courier device 308. The courier device 308 is now withinthe source beacon detection range 304. Thus, the courier device 308 candetect the source beacon 150 and proceed to match 220 the sourceidentifier and order identifier included in the source beacon 150. If amatch is detected, the courier device 308 would then transmit a beacondetection event to the courier management system 100 indicating that thecourier device 308 is within the source location 300. The beacondetection event may also include an estimate of the proximity of thesource device 302 to the courier device 308.

FIG. 3C illustrates the courier device 308 broadcasting a courier beacon152 in accordance with one embodiment. In some embodiments, the courierdevice 308 may verify its position by broadcasting a courier beacon 152in response to detecting a source beacon 150. Because the courier device308 is already within courier beacon detection range 312, the sourcedevice 302 may detect the courier beacon 152 and transmit a secondbeacon detection event to the courier management system 100.

FIG. 3D illustrates the courier device 308 coming in close proximity tothe source device 302 so that the courier may pick up the request itemsin an order in accordance with one embodiment. In order to pick up theorder at the source location 300 the courier and courier device 308 mustmove within a threshold distance (e.g., the beacon pickup proximity306). In some embodiments, the courier device 308 (or alternatively thesource device 308 if the courier device 308 is still broadcasting thecourier beacon 152) may continue to detect the source beacon 150 andestimate the distance between the two devices. Once the distance is lessthan the beacon pickup proximity 306, the courier device 308 maytransmit a beacon detection event to the content management system 100indicating that the two devices are close together. In some embodiments,the courier management system 100 will automatically indicate that thepickup has been completed as a result of receiving this beacon detectionevent as described in previous sections.

FIG. 3E illustrates the courier device 308 leaving the source location300 in accordance with one embodiment. After pickup has been completed,the courier and courier device 308 leave the source location 300 andtherefore the source beacon detection range 304. In some embodiments,the courier device 308 may determine that that the source beacon 150 isno longer being detected and may transmit a beacon detection event tothe courier management system 100 confirming that the courier device 308has left the source location 300. In some embodiments, this beacondetection event is used to determine estimated delivery times, or toconfirm pickup of an order.

The foregoing description of the embodiments of the invention has beenpresented for the purpose of illustration; it is not intended to beexhaustive or to limit the invention to the precise forms disclosed.Persons skilled in the relevant art can appreciate that manymodifications and variations are possible in light of the abovedisclosure.

Some portions of this description describe the embodiments of theinvention in terms of algorithms and symbolic representations ofoperations on information. These algorithmic descriptions andrepresentations are commonly used by those skilled in the dataprocessing arts to convey the substance of their work effectively toothers skilled in the art. These operations, while describedfunctionally, computationally, or logically, are understood to beimplemented by computer programs or equivalent electrical circuits,microcode, or the like. Furthermore, it has also proven convenient attimes, to refer to these arrangements of operations as modules, withoutloss of generality. The described operations and their associatedmodules may be embodied in software, firmware, hardware, or anycombinations thereof.

Any of the steps, operations, or processes described herein may beperformed or implemented with one or more hardware or software modules,alone or in combination with other devices. In one embodiment, asoftware module is implemented with a computer program productcomprising a computer-readable medium containing computer program code,which can be executed by a computer processor for performing any or allof the steps, operations, or processes described.

Embodiments of the invention may also relate to an apparatus forperforming the operations herein. This apparatus may be speciallyconstructed for the required purposes, and/or it may comprise ageneral-purpose computing device selectively activated or reconfiguredby a computer program stored in the computer. Such a computer programmay be stored in a non-transitory, tangible computer readable storagemedium, or any type of media suitable for storing electronicinstructions, which may be coupled to a computer system bus.Furthermore, any computing systems referred to in the specification mayinclude a single processor or may be architectures employing multipleprocessor designs for increased computing capability.

Embodiments of the invention may also relate to a product that isproduced by a computing process described herein. Such a product maycomprise information resulting from a computing process, where theinformation is stored on a non-transitory, tangible computer readablestorage medium and may include any embodiment of a computer programproduct or other data combination described herein.

Finally, the language used in the specification has been principallyselected for readability and instructional purposes, and it may not havebeen selected to delineate or circumscribe the inventive subject matter.It is therefore intended that the scope of the invention be limited notby this detailed description, but rather by any claims that issue on anapplication based hereon. Accordingly, the disclosure of the embodimentsof the invention is intended to be illustrative, but not limiting, ofthe scope of the invention, which is set forth in the following claims.

What is claimed is:
 1. A method of location verification of a computing device, the method performed by a network system and comprising: receiving, from a requesting device over one or more networks, an order request for an item; generating an order based on the order request, the order including an order identifier associated with the order and a source device identifier of a source device; transmitting, over the one or more networks, the order to the source device and to the computing device; and receiving at least one of: a verification from the computing device over the one or more networks that the computing device is within a range of the source device, the verification based on (i) a match between the source device identifier and a major identifier included in a source beacon signal broadcasted by the source device, and (ii) a match between the order identifier and a minor identifier included in the source beacon signal; or a verification from the source device over the one or more networks that the computing device is within a range of the source device, the verification from the source device based on (i) a match between a computing device identifier associated with the computing device and a major identifier included in a computing beacon signal broadcasted by the computing device, and (ii) a match between the order identifier and a minor identifier included in the computing beacon signal.
 2. The method of claim 1, wherein receiving at least one of the verification from the computing device or the verification from the source device comprises receiving a verification from each device.
 3. The method of claim 2, further comprising: verifying that the order is picked up by a user associated with the computing device responsive to the network system receiving both the verification from the computing device and the verification from the source device; and updating, in a record associated with the order request, a status of the order request responsive to verifying that the order is picked up.
 4. The method of claim 3, further comprising: transmitting an instruction to the computing device to stop broadcasting the computing beacon signal responsive to verifying the order is picked up; and transmitting an instruction to the source device to stop broadcasting the source beacon signal responsive to verifying the order is picked up.
 5. The method of claim 4, wherein the instruction to the source device is delayed such that the source device continues to broadcast the source beacon while the computing beacon signal is not broadcast.
 6. The method of claim 1, further comprising: selecting a courier associated with the computing device from among a plurality of couriers to deliver the requested item, the selection based at least on one of a location of the source device, a specified delivery location of the item, or a location of the computing device.
 7. The method of claim 1, further comprising: receiving updates from the computing device over the one or more networks of a proximity estimate of the computing device to the source device when the proximity estimate of the computing device changes, wherein the proximity estimate is an estimate of a distance between the computing device and the source device.
 8. A non-transitory computer-readable storage medium storing computer-executable instructions that, in response to executing, cause a network system comprising a processor to perform operations, comprising: receiving, from a requesting device over one or more networks, an order request for an item; generating an order based on the order request, the order including an order identifier associated with the order and a source device identifier of a source device; transmitting, over the one or more networks, the order to the source device and to a computing device; and receiving at least one of: a verification from the computing device over the one or more networks that the computing device is within a range of the source device, the verification based on (i) a match between the source device identifier and a major identifier included in a source beacon signal broadcasted by the source device, and (ii) a match between the order identifier and a minor identifier included in the source beacon signal; or a verification from the source device over the one or more networks that the computing device is within a range of the source device, the verification from the source device based on (i) a match between a computing device identifier associated with the computing device and a major identifier included in a computing beacon signal broadcasted by the computing device, and (ii) a match between the order identifier and a minor identifier included in the computing beacon signal.
 9. The non-transitory computer-readable storage medium of claim 8, wherein receiving at least one of the verification from the computing device or the verification from the source device comprises receiving a verification from each device.
 10. The non-transitory computer-readable storage medium of claim 9, wherein the operations further comprise: verifying that the order is picked up by a user associated with the computing device responsive to the network system receiving both the verification from the computing device and the verification from the source device; and updating, in a record associated with the order request, a status of the order request responsive to verifying that the order is picked up.
 11. The non-transitory computer-readable storage medium of claim 10, wherein the operations further comprise: transmitting an instruction to the computing device to stop broadcasting the computing beacon signal responsive to verifying the order is picked up; and transmitting an instruction to the source device to stop broadcasting the source beacon signal responsive to verifying the order is picked up.
 12. The non-transitory computer-readable storage medium of claim 11, wherein the instruction to the source device is delayed such that the source device continues to broadcast the source beacon while the computing beacon signal is not broadcast.
 13. The non-transitory computer-readable storage medium of claim 8, wherein the operations further comprise: selecting a courier associated with the computing device from among a plurality of couriers to deliver the requested item, the selection based at least on one of a location of the source device, a specified delivery location of the item, or a location of the computing device.
 14. The non-transitory computer-readable storage medium of claim 8, wherein the operations further comprise: receiving updates from the computing device over the one or more networks of a proximity estimate of the computing device to the source device when the proximity estimate of the computing device changes, wherein the proximity estimate is an estimate of a distance between the computing device and the source device.
 15. A computer system comprising: one or more computer processors for executing computer program instructions; and a non-transitory computer-readable storage medium storing instructions executable by the one or more computer processors to perform steps comprising: receiving, from a requesting device over one or more networks, an order request for an item; generating an order based on the order request, the order including an order identifier associated with the order and a source device identifier of a source device; transmitting, over the one or more networks, the order to the source device and to a computing device; and receiving at least one of: a verification from the computing device over the one or more networks that the computing device is within a range of the source device, the verification based on (i) a match between the source device identifier and a major identifier included in a source beacon signal broadcasted by the source device, and (ii) a match between the order identifier and a minor identifier included in the source beacon signal; or a verification from the source device over the one or more networks that the computing device is within a range of the source device, the verification from the source device based on (i) a match between a computing device identifier associated with the computing device and a major identifier included in a computing beacon signal broadcasted by the computing device, and (ii) a match between the order identifier and a minor identifier included in the computing beacon signal.
 16. The system of claim 15, wherein receiving at least one of the verification from the computing device or the verification from the source device comprises receiving a verification from each device.
 17. The system of claim 16, wherein the steps further comprise: verifying that the order is picked up by a user associated with the computing device responsive to the network system receiving both the verification from the computing device and the verification from the source device; and updating, in a record associated with the order request, a status of the order request responsive to verifying that the order is picked up.
 18. The system of claim 17, wherein the steps further comprise: transmitting an instruction to the computing device to stop broadcasting the computing beacon signal responsive to verifying the order is picked up; and transmitting an instruction to the source device to stop broadcasting the source beacon signal responsive to verifying the order is picked up.
 19. The system of claim 18, wherein the instruction to the source device is delayed such that the source device continues to broadcast the source beacon while the computing beacon signal is not broadcast.
 20. The system of claim 15, wherein the steps further comprise: selecting a courier associated with the computing device from among a plurality of couriers to deliver the requested item the selection based at least on one of a location of the source device, a specified delivery location of the item, or a location of the computing device. 